\pard\tx7140\b0\fs28\li2100 INHERITS FROM TextConverter\
\fs16 \
\fs28 DECLARED IN MacToNeXTText.h\
\fs16 \
\
\
\fs28 CLASS DESCRIPTION\
\fs16 \
\pard\tx3120\tx3620\tx4120\fs28\li2620 The MacToNeXTText class serves to convert raw text using the standard Mac character set to the standard NeXT character set. It accomplishes this by overriding the methods provided by TextConverter class, and introducing its own conversion algorithms instead. See the TextConverter class document for details about the way one of these classes works.\
\fs16 \
\fs28 There are zillions of fonts on the Mac. Apple introduced a set with the Macintosh originally. The general layout for these type families is defined in Inside Macintosh Volume 1 page 221 (many of the fancy families, like San Francisco, do not have all the characters listed in the table). With the LaserWriter Plus came several new type families, and these used a superset of the character set defined in Inside Mac. This class understands the superset used by faces such as Avant Garde, Bookman, etc. This is just to say that it will do a reasonable job of converting Mac text that was created using any of Apple's type families to NeXT text. When they extend themselves beyond the basic ASCII character set, third parties, both commercial and non commercial, often create their own character mappings which may or may not have any relation to Apple's. This class can not garantee to process those correctly. Recognizing that some fonts may have stuck strictly to the table in Inside Mac, and then done their own thing in the undefined character spaces, this object allows one to toggle a mode with SetMode:. If passed YES, it will convert only those characters defined in the Inside Mac table. If NO, it will use the full table as shown in the LaserWriter families. The default is NO.\
\pard\tx7140\fs16\li2100 \
\pard\tx3120\tx3620\tx4120\fs28\li2620 A table listing the conversions done by this class is provided at the end.\
\fs16 \
\pard\tx7140\li2100 \
\
\fs28 INSTANCE VARIABLES\
\fs16 \
\pard\tx7140\tx10180\tx10680\i\fs28\fi-4540\li7140 Declared in MacToNeXTText
\pard\tx3120\tx3620\tx4120\b0\fs28\li2620 This returns a single character in the NeXTstep character encoding set that most closely matches the specified Macintosh character. If the match can not be made exactly, this sets the error to
\pard\tx3120\tx3620\tx4120\b0\fs28\li2620 This behaves as documented in the TextConverter class: it converts data from the source string to a destination string it creates, and it then returns this string with its length. See the description above, and the table below, for encoding details. \
\pard\tx7140\fs16\li2100 \
\b \
\fs28 init\
\pard\f1\b0\fi-1020\li3620 -
\f0 (Instance)
\b init\
\pard\tx3620\b0\fi-380\li3620 0 Result codes and test\
\pard\tx3120\tx3620\tx4120\b0\fs28\li2620 This allows the caller to specify whether future conversions should use only the table found in Inside Macintosh Volume I, p. 221. or use the character set (which is a superset of the former) used by the families that are used with the LaserWriters. The only reason to specify YES (i.e. use the restricted IM V1 table) is if one is converting some older text which made use of those upper characters in other ways, and one doesn't want them to be shuffled around. This is just to say: the odds are REAL good that you won't ever use this. \
\pard\tx3120\tx3620\tx4120\li2620 Characters from 0x00 to 0x79 are converted exactly as the superclass converts them, with the following exceptions (the second is to convert the line termination character)\
\pard\tx3120\tx3620\tx4120\b0\fs24\li2620 Characters above 0x79 are converted as detailed in the following columns. Note that an entry of `
\fc0 ——' means that the specified Mac character could not be converted. When this occurrs, the object returns the Mac character code, and sets an error value. If the strict Inside Mac V. 1 flag is set, then all characters above D8 are returned as themselves with no error (as shown in column 5). If one uses the ConvertString method, the object returns the values detailed in column 4. Note that these never return a value of `——', but instead return the name of the character it could not convert. (the values with `——' in the final column will get the strings showin the ConvertString column if this flag is set when calling that method). Finally note that the first four characters are only actually found in Chicago. However, they shouldn't be turning up, in general, in other fonts, so I took the liberty of including them here. \
